-
Notifications
You must be signed in to change notification settings - Fork 217
Add netstandard2.1
target and update DiagnosticSource
dependency
#2679
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
🤖 GitHub commentsExpand to view the GitHub comments
Just comment with:
|
🔍 Preview links for changed docs |
I updated to the .NET 9 SDK and that I suspect is triggering the new formatting warnings, but I'm not entirely sure why. Will work on resolving those. |
8d5b054
to
5ddfaca
Compare
Working on the test failures. The IIS ones suggest we might still have to ship an older DiagnosticsSource build too, although I need to investigate why exactly based on our packaging process. |
067043d
to
b99f3da
Compare
e8607fd
to
c9b0b45
Compare
2b6ca25
to
b5fba58
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Fixes #2657
Fixes #2445
This adds a
netstandard2.1
target so that features such as OTel bridge are available on older runtimes, even though those are out of support. This prevents an update of our package, without a runtime update, breaking/removing features. Features may still not be 100% compatible with older unsupported runtimes, but should work in general.As part of this, I updated the minimum dependency for
System.Diagnostics.DiagnosticSource
which is no generally 8.0.0. We still ship a version ofElastic.Apm
and loader for the Startup hooks zip file which are built against 6.0.0. These support older unsupported runtimes although with no official testing.NOTE: We DOT NOT update
System.Diagnostics.DiagnosticSource
onnet462
andnet472
. While this worked and tested fine in local dev, it fails the IIS tests in CI. For now, we leave the version in these targets unchanged from 5.0.0. This is likely fine as we do not depend on any newer APIs in those targets.Compiler pre-processor directives now prefer
NET
over a specific .NET version. We also addNETSTANDARD2_1
so that features continue to work on older runtimes without a specific .NET target, i.e. 6 and 7.Docs PR to follow.